- CONFLICT-RESOLUTION.md: cite router-coherence v2 ADR as current,
  v1 retained as historical record (finding #1).
- ROUND-HISTORY.md: correct operator-algebra spec line count in
  Arc 2 narrative (324 -> 365; both duplicated occurrences) to
  match the shipped spec at `e51ec1b` (finding #2).
- openspec-coverage-audit: drop broken link to non-existent
  inventory follow-up; band definitions already live in Part C
  (finding #3). Attribute triggering question to "human maintainer"
  per write-for-a-stranger norm (finding #8).
- best-practices-scratch: merge split H2 "uv-only Python package
  and tool / management" into single heading (finding #4).
- memory-role-restructure-plan: add --exclude-dir=references to
  baseline grep loops so research scratch doesn't inflate hit
  counts (finding #5); canonicalize flat-file destination to
  persona-roles-README.md to match the sed rewrites below
  (finding #6); replace three non-portable `xargs -r sed -i ""`
  invocations with portable `while read + sed -i.bak + rm` loops
  that work on BSD and GNU alike (finding #7 and two sibling
  instances of the same bug).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…-round v2 supersedure + DORA substrate (#31)

* Round 41: OpenSpec coverage audit + backfill-program ADR

Answers Aaron 2026-04-20 delete-all-code-recovery question:
4 capabilities / 783 lines of spec.md vs 66 top-level F#
modules / 10,839 lines under src/Core/ — ~6% coverage today.

docs/research/openspec-coverage-audit-2026-04-21.md
- Inventory of 66 modules with line counts + capability
  mapping for the 4 existing capabilities
- Uncovered modules sorted by delete-recovery blast radius:
  Band 1 MUST BACKFILL (8 modules / 1,629 lines — ZSet,
  Circuit, NestedCircuit, Spine family, BloomFilter as
  Adopt-row compatibility-coupling exception), Band 2 HIGH
  (12 / 2,008), Band 3 MEDIUM (45 / 6,585), Band 4
  deliberately uncovered (AssemblyInfo only)
- First 6-round cadence: operator-algebra extension (41),
  lsm-spine-family (42), circuit-recursion (43),
  sketches-probabilistic (44), content-integrity (45),
  crdt-family (46)
- Success signal = Viktor spec-zealot adversarial audit:
  "could I rebuild this module from this spec alone?"

docs/DECISIONS/2026-04-21-openspec-backfill-program.md
- Adopts one-capability-per-round baseline with paper-grade
  half-credit rule (no more than 1 paper-grade round per 3)
- Band 1 priority until complete; Adopt-row escalation for
  BloomFilter (TECH-RADAR Adopt without spec contract is a
  backwards-compatibility hazard)
- Round-close ledger gains an `OpenSpec cadence` line
- Alternatives considered: big-bang backfill (rejected —
  ontology-landing cadence + reviewer bandwidth), per-module
  capabilities (rejected — loses cross-module invariants),
  organic prioritisation (rejected — 40 rounds of drift
  evidence)

docs/BACKLOG.md
- Collapses the 29-line P0 scope into a 15-line pointer at
  the inventory + ADR now that parts (a)-(e) of the program
  setup have landed. Remaining work = per-round capability
  backfill per ADR schedule.

Build: dotnet build -c Release clean; BP-10 ASCII-clean on
all 3 modified files; markdownlint-cli2 clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: operator-algebra spec extension (cadence ship)

First ship under the OpenSpec backfill program adopted
2026-04-21. Extends openspec/specs/operator-algebra/spec.md
(184 -> 324 lines) with five new requirements covering
structural and lifecycle gaps that the existing mathematical-
law coverage left implicit:

1. Operator lifecycle — construction / step / after-step /
   reset phases with side-effect-freedom on construction and
   epoch-replay semantics on reset
2. Strict operators break feedback cycles — formalises that
   z^-1-on-feedback is a scheduling prerequisite and that
   cycle-without-strict is a construction error, not a
   silent heuristic
3. Clock scopes and tick monotonicity — nested-scope-to-
   fixpoint rule + sibling-scope independence
4. Incremental-wrapper preserves the chain rule —
   Incrementalize(Q) observably equivalent to D . Q . I,
   with linear/bilinear substitution permitted as an
   optimisation
5. Representation invariants of the reference Z-set —
   O(n+m) group ops + zero-alloc iteration as the reference
   contract; hash-table recoveries permitted at documented
   perf trade-off

Disaster-recovery effect: a contributor with only this spec
(plus the durability-modes + retraction-safe-recursion specs)
can now rebuild Circuit.fs Op base + Incremental.fs wrapper +
ZSet.fs representation invariants from the spec text alone.

Owner: Architect (Kenji). Adversarial audit by Viktor
(spec-zealot) is the ADR-declared ship-gate and will run
post-land.

Build: not rebuilt (no F# source changed); markdownlint
clean; BP-10 ASCII clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: close Viktor P0 findings on operator-algebra spec

Viktor's adversarial audit of the Round 41 cadence ship (commit
e51ec1b) surfaced four P0 findings against the disaster-recovery
bar. This commit closes all four:

- **P0-1 (namespace drift).** `profiles/fsharp.md` asserted
  `Dbsp.Core` throughout, but `src/Core/**` uses `Zeta.Core`. A
  spec-only recovery would have shipped the wrong namespace to
  every downstream consumer. Replaced via one `replace_all` Edit.

- **P0-2 (phantom Reset method).** The lifecycle requirement
  claimed a `reset` phase that does not exist on `Op`. Replaced
  the "reset replays the epoch" scenario with a
  determinism-under-structural-equivalence property: two
  freshly-constructed circuits of the same topology, stepped
  with the same input sequence, MUST produce identical outputs
  at every tick. Reconstruction is the supported route to a
  replayed epoch.

- **P0-3 (after-step scope).** The lifecycle requirement said
  after-step runs "after every operator in the scope has
  completed its step." `Circuit.fs:205-208` iterates the
  `strictN` array only — after-step is selective to strict
  operators. Fixed wording and added a "after-step is selective
  to strict operators" scenario that pins the invariant.

- **P0-4 (lifecycle phase undercount).** The requirement named
  four phases (construction / step / after-step / reset) but
  the code has five (construction / step / after-step /
  clock-start / clock-end). Restructured to three per-tick
  phases plus two scope-boundary phases, and extended the
  "clock scopes and tick monotonicity" requirement with the
  scope-boundary lifecycle contract (clock-start before tick 0
  of a scope, clock-end after fixpoint or iteration cap).

Build green (0 warnings / 0 errors). BP-10 lint clean. The
capability now reflects the code's observable shape rather than
an idealised cleaner cousin; a delete-recovery from this spec
produces Zeta.Core with strict-operator after-step selectivity
and nested-scope clock-boundary phases.

Viktor's 10 P1 findings (async lifecycle, memory-ordering fence,
register-lock semantics, IncrementalDistinct surface, ZSet sort
invariant, Checked arithmetic, bilinear-size overflow,
convergence-vs-cap) are deferred to Round 42 — filed as a
BACKLOG sweep in follow-up work.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: file Viktor P1 findings as Round 42 BACKLOG absorb

Companion to 92d7db2 (closing Viktor's four P0 findings). The
ten P1-tier surface gaps Viktor identified do not block the
disaster-recovery bar at capability-close but leave the
operator-algebra spec incomplete relative to what a delete-
recovery produces. Filed as a dedicated P0 sub-item so they
travel with the OpenSpec backfill program rather than getting
lost: async lifecycle, memory-ordering fence, register-lock
semantics, IncrementalDistinct surface, ZSet sort invariant,
Checked arithmetic, bilinear-size overflow, convergence-vs-cap,
Op.Fixedpoint predicate, DelayOp reconstruction-first-tick.

Also annotated the parent OpenSpec coverage entry with Round 41
sweep status (e51ec1b + 92d7db2, P0s closed, P1s deferred) so
the backlog accurately reflects where the program stands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: ROUND-HISTORY entry — OpenSpec backfill founding + first cadence ship

Four-arc entry at the top of the file per newest-first policy:

- Arc 1 (d435126): OpenSpec coverage audit + backfill-program
  ADR. Measured 6% coverage; declared one-capability-per-round
  baseline with paper-grade half-credit and Adopt-row priority
  escalation; banded 66 F# modules by delete-recovery blast
  radius.
- Arc 2 (e51ec1b): operator-algebra extension as Round-41
  cadence ship. Five new requirements covering lifecycle,
  strict-operator scheduling, clock scopes, Incrementalize
  wrapper, ZSet representation invariants.
- Arc 3 (92d7db2): Viktor P0 close. Four drift-from-code
  defects fixed — namespace (Dbsp.Core → Zeta.Core), phantom
  Reset, after-step scope (strict-only), lifecycle phase
  undercount (3 per-tick + 2 scope-boundary).
- Arc 4 (56f34b5): Viktor P1s filed as Round-42 absorb under
  the parent backfill P0, creating mechanical coupling between
  each capability ship and the following round's P1 sweep.

Round-41 observations for Round 42 + prospective BP-WINDOW
ledger table rendering the four commits against the consent /
retractability / no-permanent-harm axes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: memory-folder role-restructure — design plan + BACKLOG pointer

Aaron 2026-04-19 asked for memory/role/persona/ so roles become
first-class in the directory structure. Surface is wider than
it first looks — 114 files / ~260 hand-written references to
memory/persona/ paths (plus ~440 auto-regenerated references
in tools/alignment/out/ that refresh on next citations.sh run).
A bad role axis is hard to reverse; this design doc proposes
the axis and holds execution for Aaron's sign-off rather than
just-doing-it under Auto Mode.

Design plan lands at:
  docs/research/memory-role-restructure-plan-2026-04-21.md

Contents: 13-directory role axis (architect, security,
verification, review, experience, api, performance, devops,
algebra, skill-ops, maintainer, homage, alignment);
persona-to-role crosswalk for every current directory;
5-phase execution plan (pre-flight greps → git mv → sed
passes → 5-check verification → pointer-source updates);
special-case handling for aaron (human maintainer),
rodney (homage-named AI persona on the reducer skill),
sova (emerging alignment-observability role); rollback
plan (one atomic commit, git revert); four open questions
for Aaron on axis judgement-calls.

BACKLOG entry updated to reflect design-landed state with
execution-slot recommendation for Round 42 opener after the
Round 41 PR merges (keeps wide-surface reviews from
overlapping).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: actualise Rounds 37-40 BP-WINDOW ledgers (PR #30 merged)

Rounds 37-40 shipped via PR #30 (merge commit 1e30f8c, 2026-04-20).
Ledger headers updated from "(prospective)" to "(merged via PR #30,
1e30f8c)" — the BP-WINDOW scores are now settled, not forecasts.

Round 41 ledger remains "(prospective)" — round-41 branch has not
merged to main yet.

Prose uses of "prospective" on lines 437, 447, 553, etc. are
historical-narrative commentary on authoring-time methodology and
stay as-is.

* Round 41: Soraya tool-coverage audit on RecursiveSigned skeleton

Round 39 observation flagged src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla as held pending
formal-verification-expert tool-coverage review. Round 41 closes
that gate.

Soraya's notebook entry lands:

- Per-property tool table S1-S4 + refinement cross-check. TLC
  primary for S1/S2/S3/S3'/SupportMonotone; FsCheck for S4.
- S2 flagged as the one P0 on the spec (silent fixpoint drift
  unrecoverable); BP-16 requires Z3 QF_LIA cross-check.
- Refinement mapping: FsCheck cross-trace (signed vs counting at
  SeedWeight=1) wins over TLA+ refinement proof or Lean lemma —
  anti-TLA+-hammer, implementation-level where the bug bites.
- Readiness gate: TLA+ spec is ready to model-check; no pre-TLC
  pass needed. Optional round-42 follow-up: add
  PROPERTY EventuallyDone to .cfg for liveness.
- Graduation verdict: CONDITIONAL PASS. Four tool-coverage
  prereqs named in priority order; F# landing gated on them.

Files read (no edits): RecursiveSigned.fs, RecursiveSignedSemiNaive.tla
/cfg, RecursiveCountingLFP.tla, retraction-safe-semi-naive.md.

* Round 41: capture Soraya's 4 tool-coverage prereqs on RecursiveSigned

Soraya's round-41 audit of src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla landed as a CONDITIONAL
PASS for Round-42 graduation. This commit lifts the four named
prereqs out of her notebook into BACKLOG sub-items under the
parent "Retraction-safe semi-naive LFP" entry, so the round-42
opener picks them up as checkbox work rather than having to re-read
the notebook.

Prereqs in priority order:
- Prereq 1 — TLC CI wire-up (RecursiveSignedSemiNaive.cfg)
- Prereq 2 — Z3 QF_LIA lemma for S2 FixpointAtTerm (BP-16 cross-check
  on the one P0; TLC alone insufficient for silent-fixpoint-drift risk)
- Prereq 3 — FsCheck property for S4 sign-distribution (anti-
  TLA+-hammer; two-trace quantification is NOT a TLA+ property)
- Prereq 4 — FsCheck cross-trace refinement (signed vs counting
  at SeedWeight = 1); cites BP-16

Round-42 graduation gate also captured: prereqs 1-4 CI-green + F#
implementation with P1/P2/P3 enforced at caller.

* Round 41: extend ROUND-HISTORY with arcs 5-7 (post-narrative commits)

The initial Round 41 ROUND-HISTORY entry (6e6e211) covered arcs
1-4 (coverage audit, operator-algebra cadence ship, Viktor P0
close, Viktor P1 file). Three more commits landed after:

Arc 5 — ROUND-HISTORY narrative + memory-restructure design
(6e6e211, 36797ba). The memory-folder rename was downgraded to
"design plan + sign-off first" under Auto Mode's
do-not-take-overly-destructive-actions clause (700-occurrence
cross-reference surface).

Arc 6 — BP-WINDOW ledger actualisation for Rounds 37-40
(85fb352). Provenance (PR #30 / 1e30f8c) attached to each
"(prospective)" header.

Arc 7 — Round-35 holdover close (e461d9c, 15e9654). Soraya
tool-coverage audit landed CONDITIONAL PASS for Round-42
graduation; four prereqs captured as BACKLOG sub-items with
BP-16 citation on the S2 Z3 cross-check.

Also: one new observation line in the Round-42 handoff section
noting the holdover-closed-same-round-as-cadence-item pattern.
BP-WINDOW ledger gains three rows.

* Round 41: Aarav skill-tune-up ranking (catch-up from round-18 stale)

CLAUDE.md 5-10 round cadence rule was 23 rounds overdue. Round 41
is the catch-up slot. Live-search + full ranking + prune pass all
landed in a single invocation.

Live-search (4 queries, 2026-Q1/Q2 best-practices targets):
- 6 findings logged to best-practices-scratch.md: Gotchas-section
  rise, pushy-descriptions pattern, Claude-A-authors / Claude-B-
  tests, router-layer command-integrity injection class, Agent
  Stability Index 12-dim drift metric, OWASP Intent Capsule
  pattern.
- Zero contradictions with stable BP-NN rules.
- Zero promotions flagged to Architect this round; all six are
  "watch" or route-elsewhere.

Top-5 skills flagged for tune-up:
1. performance-analysis-expert (642 lines, 2.1x BP-03 cap) — SPLIT — M
2. reducer (570 lines) — SPLIT or TUNE (prune) — M
3. consent-primitives-expert (507 lines) — SPLIT honouring BP-23
   theory/applied axis — M
4. claims-tester / complexity-reviewer router-coherence drift —
   HAND-OFF-CONTRACT — S (round-18 carry-over)
5. skill-tune-up (self) — 303 lines, 3 over BP-03 — TUNE (prune
   authoritative-sources duplicated with AGENT-BEST-PRACTICES.md)
   — S. Self-flagged first per BP-06.

Notebook state:
- Stale round-18 top-5 archived in Pruning log (first catch-up prune).
- 912 words, well under 3000-word BP-07 cap.
- ASCII-only, BP-10 clean.

Nine more bloat-row skills named as notable mentions queue behind
the top-3 bloat cases.

* Round 41: ADR — claims-tester/complexity-reviewer hand-off contract

Close Aarav's round-18 HAND-OFF-CONTRACT finding (carried 23 rounds
after ranker went offline by cadence). Two-stage pipeline: analytic
bound first (complexity-reviewer), empirical measurement second
(claims-tester). Names the reverse trigger (benchmark surprise flows
the other direction) and the decision table for who fires when.
Follow-up SKILL.md edits route via skill-creator per GOVERNANCE §4.

* Round 41: extend ROUND-HISTORY with Arc 8 (router-coherence ADR)

Arc 8 covers the claims-tester/complexity-reviewer hand-off ADR
(47d92d8) closing Aarav's 23-round-stale round-18 HAND-OFF-CONTRACT
finding. New observation on cadence-outage-recovery as a design axis:
sweep infrastructure is subject to the same bitrot it detects on other
surfaces. BP-WINDOW ledger gains two rows (085c0e3 Aarav catch-up,
47d92d8 router-coherence ADR).

* Round 41: correct Prereq 1 sizing — no TLC CI job exists

Close-out audit surfaced that .github/workflows/gate.yml only CACHES
the tla2tools.jar artefact; nothing runs it. RecursiveCountingLFP.tla
has shipped since round 19 compile-checkable-only — 22 rounds with no
run-gate against its invariants. Soraya's Prereq 1 re-sized S→M with
expanded scope covering both specs. Finding recorded as new round-41
observation: verifier-present does not imply verifier-actually-runs.

* Round 41: BP-WINDOW ledger — 459b218 + d76a09b rows

Keeps the Round 41 BP-WINDOW ledger commit-aligned rather than
arc-aligned. 459b218 is the Arc-8 narrative itself; d76a09b is the
Prereq-1 S→M correction. Both retractable as single reverts.

* Round 41: file formal-analysis-gap-finder round-42 run — verifier-runs lens

Codifies the round-41 Prereq-1 audit finding as a tracked
research entry, distinct from its ROUND-HISTORY narrative
presence. The finding — a verifier's installation artefacts
do not imply the verifier is exercised by any CI job — is
exactly the class formal-analysis-gap-finder exists to
surface. Concrete motivating case: RecursiveCountingLFP.tla
compile-checkable-only for 22 rounds. Round-42 scope covers
the bidirectional audit (specs without gates + gates without
specs). Handoff to Soraya per the skill's standing contract;
does not write the spec or CI job (DevOps + Soraya work).
Schedules after Prereq 1 lands so the audit sees corrected
state.

* Round 41: BP-WINDOW ledger — 2042a85 row

Per the established stopping rule (meta-ledger commits do not
get self-referential rows; their round-close coverage is the
PR merge), this commit adds only the 2042a85 row and does not
add a row for itself.

* Round 41: CONFLICT-RESOLUTION — Hiroshi ↔ Daisy hand-off row

Closes ADR 47d92d8's third follow-up action item. Single-row
addition to Active tensions citing the router-coherence ADR as
the standing resolution. Doc-only edit (not a SKILL.md touch,
so GOVERNANCE §4 does not gate this). The other two ADR
follow-ups (claims-tester + complexity-reviewer SKILL.md
updates) remain deferred to round 42 via skill-creator
workflow.

* Round 41: BP-WINDOW ledger — fcfa3d9 row

Per-commit ledger discipline for the CONFLICT-RESOLUTION
Hiroshi ↔ Daisy row. Meta-ledger-only commit so no
self-referential row for this commit itself (established
stopping rule).

* Round 41: file harsh-critic findings on ADR 47d92d8 as round-42 supersedure backlog

Router-coherence ADR 47d92d8 (Hiroshi analytic ↔ Daisy empirical
two-stage pipeline) landed without the adversarial-review gate.
Post-landing harsh-critic (Kira) pass surfaced 3 P0 + 5 P1 + 2 P2
substantive findings, including (P0-1) unscoped grandfather
clause, (P0-2) table-vs-prose contradiction on reverse trigger,
(P0-3) Stage-1 "analytically wrong" clause blocking the evidence
loop for escalation, (P1-7) no escalation timebox reproducing the
23-round-stale failure mode the ADR diagnosed, (P1-8) two advisory
skills not composing to a mandatory pipeline without a binding
dispatcher, (P2-9) example-bug on BCL Dictionary.Remove amortised
complexity, and more.

File as round-42 supersedure rather than inline-edit because
docs/CONFLICT-RESOLUTION.md already cites 47d92d8 as Standing
Resolution — supersedure preserves the citation chain via
GOVERNANCE §2 edit-in-place with a "Superseded by …" header on
v1. New ADR target: docs/DECISIONS/2026-04-??-router-coherence-
v2.md. Supersedure work blocks the claims-tester +
complexity-reviewer SKILL.md updates ADR 47d92d8 follow-up work
depends on — those edits should target v2, not v1.

Owner: Architect drafts; Kira audits closure; Aarav confirms
router-coherence drift stays closed. Effort: M. Schedule: Round
42 slot after Soraya Prereq 1 (TLC wire-up) lands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW ledger — 779d7ef row

Ledger row for harsh-critic findings filing commit. Primary work
(BACKLOG addition tracking a round-42 supersedure with 10 named
findings), not meta-ledger — earns a row under the BP-WINDOW
per-commit discipline. Consent = adversarial findings tracked
honestly; Retractability = supersedure preserves citation chain
vs inline-edit; No-permanent-harm = single BACKLOG edit, no ADR
body touched, no SKILL.md touched.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 9 narrative — self-correction sweep

ROUND-HISTORY Arc 1-8 narrated primary commits up through the
router-coherence ADR (47d92d8). Four primary commits landed
after Arc 8 — Prereq 1 sizing correction (d76a09b), recurring-
audit lens BACKLOG entry (2042a85), CONFLICT-RESOLUTION Hiroshi
↔ Daisy row (fcfa3d9), and harsh-critic findings filed as
round-42 supersedure (779d7ef) — visible only in the BP-WINDOW
ledger table, not in narrative form.

Arc 9 ties them into one coherent sequence: the round's
self-correction ran unusually deep. Arc 8 corrects Aarav's
round-18 finding via ADR; Arc 9 catches the corrector itself
under-reviewed via Kira's adversarial pass. Both self-
corrections land before round-close. Narrative-ledger
alignment is the BP-WINDOW discipline's first assertion —
restoring it.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW ledger — 160fcfa row

Ledger row for Arc 9 narrative commit. Narrative extensions
count as primary work under BP-WINDOW precedent (per 459b218
and 6e6e211 examples) and earn a ledger row. Consent = drift
closed honestly; Retractability = single revertable doc edit;
No-permanent-harm = isolated insertion.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: v2 ADR — router-coherence supersedure closes 10 Kira findings in-round

Drafts v2 of the router-coherence ADR (docs/DECISIONS/2026-04-21-router-coherence-v2.md) that supersedes v1 (47d92d8) in the same round, closing all 10 Kira harsh-critic findings (3 P0 + 5 P1 + 2 P2) via named textual closures C-P0-1 through C-P2-10.

Key closures:
- C-P0-1: grandfather clause bounded with Kenji-owned inventory + one-per-round discharge
- C-P0-2: reverse trigger unconditional (table now matches prose)
- C-P0-3: escalation-evidence exception permits Stage 2 under conference protocol with explicit labelling
- C-P1-5: Stage-1 trigger widened to match claims-tester SKILL.md contract
- C-P1-7: escalation timebox (round +2 auto-promote to BACKLOG P1) prevents 23-round-stale reproduction
- C-P1-8: Kenji named as binding dispatcher — advisory + advisory + binding-dispatcher composes to mandatory pipeline
- C-P2-9: Dictionary.Remove example replaced with ArrayPool<T>.Rent (legitimate BCL-contract edge)

v1 kept in place per GOVERNANCE §2 with Superseded-by header appended in a follow-up commit so the CONFLICT-RESOLUTION Active-tensions citation chain remains resolvable.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: v1 ADR — append Superseded-by header per GOVERNANCE §2

Appends Superseded-by header to router-coherence v1 ADR (47d92d8) pointing at v2 (09f0889), per GOVERNANCE §2 (docs read as current state; superseded ADRs keep v1 in place with redirect header so citation chains remain resolvable).

Also corrects v1 Status from "Proposed — awaits sign-off" to "Accepted (pre-adversarial-review; superseded by v2 same-round after Kira pass)" per Closure C-P1-4 in v2 — Status was already cited as Standing Resolution in docs/CONFLICT-RESOLUTION.md Active-tensions, so Proposed was factually wrong.

The v1 body text is not edited — supersedure preserves the historical record; v2 carries the closures.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 10 narrative + BP-WINDOW rows for v2 supersedure

Adds Arc 10 narrative covering 09f0889 (v2 ADR) and 4efe545 (v1 Superseded-by header) as one coherent in-round supersedure story, after Arc 9's "self-correction sweep" and before Round 41 observations. Pattern: Arc 9 surfaces the under-review; Arc 10 lands the close in the same round rather than deferring a known-imperfect artefact.

Adds two BP-WINDOW ledger rows (09f0889, 4efe545) to the round-41 ledger block per the per-commit accounting discipline.

Supersedure arc count now covers the full round-41 close: 10 arcs / 25 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: close BACKLOG supersedure entry — discharged in-round by v2

Flips BACKLOG router-coherence supersedure entry from [ ] to [x] ✅ with "shipped round 41 in-round" annotation pointing at v2 ADR (09f0889) + v1 Superseded-by header (4efe545). All 10 Kira findings closed via named textual closures C-P0-1 through C-P2-10.

Original finding narrative preserved below the closure line per the shipped-item convention used elsewhere in the file (audit trail).

Follow-up SKILL.md edits to claims-tester + complexity-reviewer via skill-creator remain round-42 scope, now targeting v2 as intended.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW row for BACKLOG-close commit 4537365

Adds BP-WINDOW ledger row for 4537365 (BACKLOG supersedure entry discharged in-round) to match the Arc 9 precedent where 779d7ef (BACKLOG entry addition) received a row. Symmetry: add and close get equal ledger treatment.

Meta-ledger stopping rule still holds — this commit itself (which only adds a ledger row) does not get a self-referential row.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: grandfather O(·) claims inventory — honours v2 C-P0-1 within-round

Produces the one-time grandfather-claims inventory named in router-coherence v2 ADR §Closure C-P0-1 within the round v2 lands, per ADR's own within-round commitment.

Inventory: 35 live claims at ADR-landing time (29 F# /// docstrings in src/Core/ + src/Bayesian/, 3 grey-zone F# code comments, 1 openspec/specs/operator-algebra/spec.md line, 2 docs/research/** claims). Zero hits in root README, memory/persona/*/NOTEBOOK.md, docs/papers/** (directory does not exist yet).

Distinguishes live claims (shipping as asserted bounds) from historical evidence (BACKLOG [x] ✅ residue, TECH-RADAR flag-text narrating past regressions, in-file "was O(…)" commentary on fixed paths). Only live claims populate the grandfather set — evidence is captured for audit trail but excluded per v2's intent ("claims Zeta is currently making").

BACKLOG discharge entry added: P2, one-claim-per-round cadence, ~35-round tail, Aarav graceful-degradation clause fires on ≥3 rounds without discharge.

Complexity-class distribution of live set: 10 O(1), 13 O(log n)/O(log k)/O(log N), 7 O(n)/O(n log n)/O(n log k), 5 parametric.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 11 narrative + BP-WINDOW row for grandfather inventory

Adds Arc 11 narrative covering d98ef2b (grandfather inventory + BACKLOG discharge entry) as the close of the v2 ADR's within-round commitments. Pattern: Arc 10 lands the ADR; Arc 11 lands the ADR's own within-round commitment — without Arc 11, Arc 10 would have shipped a contract Zeta didn't meet.

Adds BP-WINDOW ledger row for d98ef2b per per-commit accounting discipline.

Round 41 now closes at 11 arcs / 30 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: DORA 2025 reports — reference substrate land in docs/

Two external-anchor PDFs (CC BY-NC-SA 4.0) placed at their
memory-documented paths:

- docs/2025_state_of_ai_assisted_software_development.pdf
  (~15MB, 138 pages) — findings + data report.
- docs/2025_dora_ai_capabilities_model.pdf (~9MB, 94 pages)
  — framework companion.

Citation anchors this commit makes in-tree rather than
memory-only: Nyquist stability criterion for AI-accelerated
development (foreword p9 fn 1) as theoretical anchor for
CI-meta-loop + retractable-CD P1 BACKLOG work; "AI is an
amplifier" anchor that echoes the corporate-religion /
sandbox-escape threat class; seven-capability AI model that
gives the external measurement vocabulary for round-audit
output (capability #7 "quality internal platforms" is the
in-flight P1 cluster per 2026-04-20 memory).

License note: derived work is NC-SA-bound; Zeta citations
are fine, external redistribution inherits NC-SA. Paired
companion memory file is reference_dora_2025_reports.md
(out-of-tree); this commit brings the primary sources
in-tree so citation from research docs + ADRs can point
at a repo-local path rather than a newsletter-gated URL.

* Round 41: Arc 12 narrative + BP-WINDOW row for DORA substrate

Narrative section for Arc 12 inserted before "Round 41
observations for Round 42" with primary commit pointer to
46075d6. Arc 12 frames the DORA 2025 PDFs as
memory-promotion substrate per the 2026-04-20 feedback entry
("DORA is our starting point for measurements") and cites
the concrete in-tree anchors (Nyquist p9 fn 1, seven-
capability model, AI-amplifier thesis).

Also surfaces honestly — in-body, not buried in a private
retrospective — the ranker-scope gap that let the two
untracked PDFs sit 18+ hours through nine consecutive
/next-steps invocations before this arc closed the gap. The
skill explicitly lists docs/research/ and docs/TECH-RADAR.md
but not `git status --short` for untracked files. Candidate
skill-tune-up note for Aarav's notebook: /next-steps must
run `git status --short` on every invocation so dropped-in
artefacts appear in ranking before the ninth re-fire, not
after.

BP-WINDOW ledger gets a matching 46075d6 row with
reference-document-specific cells: Consent strengthened by
promoting memory-only anchors to in-repo substrate and by
surfacing the ranker-stall pattern in-narrative; retraction
is a single `git rm` if the license / size stance later
changes; no-permanent-harm preserved since no runtime
behaviour depends on the PDFs' presence (they are citation
substrate, not loaded artefacts).

Arc count now 12; primary-work-commit count now 12 (Round 41
alignment preserved). Build gate green (0 Warning / 0 Error);
BP-10 lint clean on the narrative + ledger row.

* Round 41: markdownlint CI fix on PR #31

Three rule violations surfaced by `lint (markdownlint)` CI job on
PR #31:

- `docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md:261`
  MD022/blanks-around-headings — collapse multi-line heading
  `## Decision rationale (one paragraph for the\nwait-don't-read
  audience)` to a single line so the parser stops seeing line 262
  as adjacent non-blank content.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:106`
  MD032/blanks-around-lists — add blank line between "Surface
  distribution:" lead-in and the `-` list that follows.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:111`
  MD032/blanks-around-lists — same fix for "Complexity-class
  distribution (rough):" lead-in.

All three are the same class of fix shipped in task #105 on PR #30.
Additive edit to the open round-41 PR branch — no rewrite of shipped
content, semantics preserved.

Verified clean via `npx markdownlint-cli2` on both files before push.

* Round 41: address 8 Copilot inline review findings on PR #31

- CONFLICT-RESOLUTION.md: cite router-coherence v2 ADR as current,
  v1 retained as historical record (finding #1).
- ROUND-HISTORY.md: correct operator-algebra spec line count in
  Arc 2 narrative (324 -> 365; both duplicated occurrences) to
  match the shipped spec at `e51ec1b` (finding #2).
- openspec-coverage-audit: drop broken link to non-existent
  inventory follow-up; band definitions already live in Part C
  (finding #3). Attribute triggering question to "human maintainer"
  per write-for-a-stranger norm (finding #8).
- best-practices-scratch: merge split H2 "uv-only Python package
  and tool / management" into single heading (finding #4).
- memory-role-restructure-plan: add --exclude-dir=references to
  baseline grep loops so research scratch doesn't inflate hit
  counts (finding #5); canonicalize flat-file destination to
  persona-roles-README.md to match the sed rewrites below
  (finding #6); replace three non-portable `xargs -r sed -i ""`
  invocations with portable `while read + sed -i.bak + rm` loops
  that work on BSD and GNU alike (finding #7 and two sibling
  instances of the same bug).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: fix markdownlint MD024 — remove duplicate Round 41 block

The 5-file merge that resolved PR #31's rebase left two identical
copies of the whole Round 41 section in docs/ROUND-HISTORY.md (375
lines each), which tripped MD024/no-duplicate-heading on the
`## Round 41` headings at lines 651 and 1028. The two blocks were
bit-identical (including the just-corrected "365 lines" drift fix),
so the fix is a simple deletion of the second block — the first
block is kept as the canonical Round 41 history.

markdownlint-cli2 now reports clean on docs/ROUND-HISTORY.md.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: revert 324→365 (historically wrong); finish Copilot follow-ups

Two fixes on PR #31:

1. ROUND-HISTORY.md: revert "324 → 365" change from Finding #2.
   Copilot's suggestion was based on a stale intermediate snapshot.
   At Arc 2 ship commit `e51ec1b`, the spec was exactly 324 lines
   (verified via `git show e51ec1b:openspec/specs/operator-algebra/spec.md | wc -l`).
   Reframed with commit-pin ("Spec size at Arc 2 ship (`e51ec1b`)
   was 324 lines; subsequent Viktor closure arcs in this same round
   grew it further") so future drift-checks recognize it as a
   historical anchor, not a current-state claim.

2. memory-role-restructure-plan-2026-04-21.md: close four follow-up
   Copilot findings in one sweep. All Phase 1 + Phase 3 grep
   invocations now consistently use `--exclude-dir=.git
   --exclude-dir=references` (dropping the piped `grep -v "^./\.git"`
   intermediate), and the three `xargs -r sed -i ""` invocations are
   replaced with portable `while IFS= read -r file; do sed -i.bak ...`
   loops (BSD/GNU compatible — the original flags were
   GNU-xargs-only and BSD-sed-only).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Fifth and final Overlay A migration for the 2026-04-23
cadence: semiring-parameterized-zeta regime-change project
memory. Queue now zero on signal-in-signal-out composes-with
set.

2026-04-23 cadence summary: 5 Overlay A migrations + courier
protocol + Amara deep-research absorb + fresh-session-quality
BACKLOG row + AutoDream policy + soulfile staged absorption.
10+ PRs, all self-scheduled free work.

Five lint-classes now identified as absorb-time-common
(MD003, MD018, MD022, MD026, MD032) — memory-author-template
recommendations noted for future fresh-writes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ntory BACKLOG (#165)

Two self-scheduled PRs this tick:
- PR #164 — Overlay A migration #5 (semiring-parameterized-zeta);
  queue zero on signal-in-signal-out composes-with set
- PR #165 — P1 BACKLOG row for factory technology inventory
  + OpenAI web UI addition (Aaron 2026-04-23 directive)

2026-04-23 day summary: ~12 durable PRs of factory work, all
self-scheduled free work under the 2026-04-23 scheduling-
authority rule.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…r cadenced audit)

Aaron 2026-04-23 directive: "we probalby need some meta
iteam to refactor the backlog base on current knowledge and
look for overlap, this is hygene we could run from time to
time so our backlog is not just a dump".

Landed as FACTORY-HYGIENE row #54 (PR #166) + per-user
feedback memory. 5-pass audit (overlap / staleness /
priority / knowledge-absorb / document). Same cadence as
sibling meta-hygiene rows (#5 / #23 / #38 / #46).

Numbered #54 to avoid collision with #53 on the AutoDream
branch (PR #155, still open).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…absorbed

PR #170 lands docs/FACTORY-TECHNOLOGY-INVENTORY.md with
~26 first-pass rows (language runtimes / data infra / agent
harnesses / formal verification / static analysis + security
/ CI + publishing).

Aaron 2026-04-23 PQC mandate absorbed as per-user feedback
memory + Open follow-up #5 on the tech-inventory doc:
quantum-resistant crypto mandatory for all factory adoption;
classical requires ADR + maintainer sign-off + replacement
plan.

Restraint reversal from auto-loop-65: scheduling rule isn't
"never open PRs" — open when the work advances.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…er-DSL / LINQ / signal-proc + KSK canonical expansion

Four new P1 post-v1-roadmap rows + one row updated:

1. **Per-entry-point F# DSLs + industry-standard surfaces**
   (Otto-139 + Otto-146). Graph gets GQL ISO 39075 / Cypher /
   Gremlin / SPARQL / Datalog survey; temporal gets Esper EPL
   / Flink SQL; time-series gets Flux / PromQL / KQL; claim /
   detect / authorize stay Zeta-native (no industry standard
   fits). Aaron clarifier "i know there are graph standards"
   acknowledged — GQL / Cypher / Gremlin are the top three.

2. **F# DSL composition + container-DSL pattern** (Otto-147
   final question). Answer: YES, F# supports DSL composition
   via nested CEs, `MergeSources` (F# 5+), custom operations,
   builder delegation. Aaron's "container DSL" guess is
   exactly the right pattern name. Implementation plan: top-
   level `zeta { }` container CE that hosts child builders
   (graph / claims / stream / signal / authorize / detect)
   via `MergeSources` + folded state. Retraction-native
   semantics bubble through container. Prior art: FParsec,
   Giraffe, SAFE Stack.

3. **LINQ-compatible entry points for C# on every F# DSL**
   (Otto-148). `IQueryable<T>` + `IGraphQueryable<TNode>` +
   `IStreamQueryable<T>` + `ISignalQueryable<T>` +
   `IClaimQueryable<T>`. Clever mapping goal: auto-generate
   LINQ provider from F# CE via the `query` translator where
   feasible, not hand-written mirrors. Expression-tree
   preservation — LINQ lowers to same Zeta operator IR.

4. **Signal-processing primitives — FFT, Hilbert, windowing,
   filters** (Otto-149). Standing approval to land whenever
   cadence permits. Unblocks Amara 17th-ferry correction #5
   Option B (Hilbert-based phase pipeline). Placement:
   `src/Core/SignalProcessing.fs` new module +
   `hilbertPhase` addition to `src/Core/PhaseExtraction.fs`.

Also updated:

- **KSK naming doc row** (line 4278). Max-coordination gate
  LIFTED per Aaron Otto-140 (*"Coordination required: Max
  per Otto-77 change whatever you need, max created the ksk
  at my direction, it's my and amaras idea, he just commited
  some inital starting point, all completely rewritable"*).
  Canonical expansion locked per Aaron Otto-142..145 self-
  correction: *"kinetic safeguare Kernel, i did the wrong
  name / it is what amara said / kinetic safeguard kernel"*.
  Resolves Amara 16th-ferry correction #7. "Kernel" here =
  safety-kernel / security-kernel sense (Anderson 1972,
  Saltzer-Schroeder reference-monitor, aviation safety-
  kernel) — NOT OS-kernel-mode. Max attribution preserved as
  initial-starting-point contributor per Otto-77. Priority
  elevated P3 → P2.

Filed per Aaron's "backlog" directive plus verify-before-
deferring discipline — prior summary claim that these rows
had already landed turned out to be hallucination; git log
confirmed only the (now-updated) KSK row existed pre-tick.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ignal-proc + KSK (supersedes #334 DIRTY) (#341)

* backlog: Aaron Otto-139..149 multi-directive block — F# DSL / container-DSL / LINQ / signal-proc + KSK canonical expansion

Four new P1 post-v1-roadmap rows + one row updated:

1. **Per-entry-point F# DSLs + industry-standard surfaces**
   (Otto-139 + Otto-146). Graph gets GQL ISO 39075 / Cypher /
   Gremlin / SPARQL / Datalog survey; temporal gets Esper EPL
   / Flink SQL; time-series gets Flux / PromQL / KQL; claim /
   detect / authorize stay Zeta-native (no industry standard
   fits). Aaron clarifier "i know there are graph standards"
   acknowledged — GQL / Cypher / Gremlin are the top three.

2. **F# DSL composition + container-DSL pattern** (Otto-147
   final question). Answer: YES, F# supports DSL composition
   via nested CEs, `MergeSources` (F# 5+), custom operations,
   builder delegation. Aaron's "container DSL" guess is
   exactly the right pattern name. Implementation plan: top-
   level `zeta { }` container CE that hosts child builders
   (graph / claims / stream / signal / authorize / detect)
   via `MergeSources` + folded state. Retraction-native
   semantics bubble through container. Prior art: FParsec,
   Giraffe, SAFE Stack.

3. **LINQ-compatible entry points for C# on every F# DSL**
   (Otto-148). `IQueryable<T>` + `IGraphQueryable<TNode>` +
   `IStreamQueryable<T>` + `ISignalQueryable<T>` +
   `IClaimQueryable<T>`. Clever mapping goal: auto-generate
   LINQ provider from F# CE via the `query` translator where
   feasible, not hand-written mirrors. Expression-tree
   preservation — LINQ lowers to same Zeta operator IR.

4. **Signal-processing primitives — FFT, Hilbert, windowing,
   filters** (Otto-149). Standing approval to land whenever
   cadence permits. Unblocks Amara 17th-ferry correction #5
   Option B (Hilbert-based phase pipeline). Placement:
   `src/Core/SignalProcessing.fs` new module +
   `hilbertPhase` addition to `src/Core/PhaseExtraction.fs`.

Also updated:

- **KSK naming doc row** (line 4278). Max-coordination gate
  LIFTED per Aaron Otto-140 (*"Coordination required: Max
  per Otto-77 change whatever you need, max created the ksk
  at my direction, it's my and amaras idea, he just commited
  some inital starting point, all completely rewritable"*).
  Canonical expansion locked per Aaron Otto-142..145 self-
  correction: *"kinetic safeguare Kernel, i did the wrong
  name / it is what amara said / kinetic safeguard kernel"*.
  Resolves Amara 16th-ferry correction #7. "Kernel" here =
  safety-kernel / security-kernel sense (Anderson 1972,
  Saltzer-Schroeder reference-monitor, aviation safety-
  kernel) — NOT OS-kernel-mode. Max attribution preserved as
  initial-starting-point contributor per Otto-77. Priority
  elevated P3 → P2.

Filed per Aaron's "backlog" directive plus verify-before-
deferring discipline — prior summary claim that these rows
had already landed turned out to be hallucination; git log
confirmed only the (now-updated) KSK row existed pre-tick.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(#341): 3 review-thread P1/P2s on F# DSL BACKLOG row

Active PR-resolve-loop on #341.

1. ISO GQL 39075 citation (thread 59WKAJ, P2): imprecise
   citation replaced with canonical form "ISO/IEC
   39075:2024 (GQL)" — Graph Query Language. Easier for
   readers to validate against the actual standard's
   indexing.

2. MergeSources / and! cross-builder claim (thread
   59WKAv, P1): clarified that MergeSources works
   WITHIN a single active CE builder that defines
   Source/MergeSources members for compatible types —
   NOT across fundamentally different DSL builders. The
   original wording read as if `graph + veridicality +
   signal` DSLs could combine directly in one `and!`
   chain; that's misleading. True cross-DSL combination
   requires the container-DSL pattern (next row's
   top-level `zeta { }` CE with child-builder
   delegation via its own Source overloads). Rewording
   makes the distinction explicit.

3. Brittle line-reference `row 4278 (KSK)` (thread
   59WKBD, P1): replaced line-number cross-refs with
   title/section-anchor cross-refs. "row 733 (F# DSL
   reimagining SQL)" / "row 719 (LINQ integration)"
   / "row 4278 (KSK)" → "the F# DSL reimagining SQL
   row (P1 SQL-frontend section)" / "LINQ integration
   row (same section)" / "KSK naming definition doc
   row (P2 research-grade section)". Titles survive
   BACKLOG row-reordering; line numbers don't.

All 3 threads have substantive replies pending via
GraphQL (next step same tick).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…18th graduation (Amara #4 robust)

Two ships consolidated per the 'parallel PRs hit positional
conflicts on tail-append' lesson:

1. RobustStats.robustZScore
   (baseline: double seq) -> (measurement: double) -> double option
   Returns (measurement - median) / (1.4826 · MAD). The 1.4826
   constant scales MAD to be consistent with Gaussian stddev.
   MadFloor prevents blow-up when every baseline value equal.

2. Graph.coordinationRiskScoreRobust
   alpha beta eigenTol eigenIter lpIter
   (baselineLambdas: double seq) (baselineQs: double seq)
   (attacked: Graph<'N>) -> double option
   Upgrades coordinationRiskScore (PR #328) from raw linear
   differences to robust-standardized z-scores per Amara
   17th-ferry correction #4. Caller provides baseline metric
   distributions; Z-scores calibrate thresholds from data.

Why robust z-scores: adversarial data isn't normally
distributed. An attacker can poison a ~normal distribution
by adding a few outliers that inflate stddev, making
subsequent real attacks look 'within one sigma'. Median+MAD
survives ~50% adversarial outliers. Standard move in robust
statistics literature; Amara's correction puts it on the
Zeta composite.

Tests (5 new; total 39 since main hasn't merged #331/#332 yet):
- robustZScore None on empty baseline
- robustZScore of measurement = median is 0
- robustZScore scales MAD by 1.4826 for Gaussian consistency
  (measurement 4 on baseline [1..5] ≈ 0.674)
- coordinationRiskScoreRobust fires strongly on K4-injected graph
  given 5 baseline samples
- coordinationRiskScoreRobust returns None on empty baselines

BACKLOG rows added this tick per Aaron Otto-139 directives:
1. Signal-processing primitives (FFT + Hilbert) — unblocks
   Amara correction #5 Option B; Aaron standing-approval
2. F# DSL for entry points + graph-query-language standards
   compliance (Cypher / GQL / Gremlin / SPARQL / Datalog)
3. LINQ-compatible entry points for C# consumers — pair with
   F# DSL; two frontends, one algebraic backend

6 of 8 Amara 17th-ferry corrections now shipped or confirmed:
Remaining: #6 ADR phrasing (already fine); #7 KSK naming
(BACKLOG #318 Max coord pending); #8 SOTA humility
(doc-phrasing discipline ongoing).

Build: 0 Warning / 0 Error.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…mara #4 robust) + 3 BACKLOG rows (#333)

* core: RobustStats.robustZScore + Graph.coordinationRiskScoreRobust — 18th graduation (Amara #4 robust)

Two ships consolidated per the 'parallel PRs hit positional
conflicts on tail-append' lesson:

1. RobustStats.robustZScore
   (baseline: double seq) -> (measurement: double) -> double option
   Returns (measurement - median) / (1.4826 · MAD). The 1.4826
   constant scales MAD to be consistent with Gaussian stddev.
   MadFloor prevents blow-up when every baseline value equal.

2. Graph.coordinationRiskScoreRobust
   alpha beta eigenTol eigenIter lpIter
   (baselineLambdas: double seq) (baselineQs: double seq)
   (attacked: Graph<'N>) -> double option
   Upgrades coordinationRiskScore (PR #328) from raw linear
   differences to robust-standardized z-scores per Amara
   17th-ferry correction #4. Caller provides baseline metric
   distributions; Z-scores calibrate thresholds from data.

Why robust z-scores: adversarial data isn't normally
distributed. An attacker can poison a ~normal distribution
by adding a few outliers that inflate stddev, making
subsequent real attacks look 'within one sigma'. Median+MAD
survives ~50% adversarial outliers. Standard move in robust
statistics literature; Amara's correction puts it on the
Zeta composite.

Tests (5 new; total 39 since main hasn't merged #331/#332 yet):
- robustZScore None on empty baseline
- robustZScore of measurement = median is 0
- robustZScore scales MAD by 1.4826 for Gaussian consistency
  (measurement 4 on baseline [1..5] ≈ 0.674)
- coordinationRiskScoreRobust fires strongly on K4-injected graph
  given 5 baseline samples
- coordinationRiskScoreRobust returns None on empty baselines

BACKLOG rows added this tick per Aaron Otto-139 directives:
1. Signal-processing primitives (FFT + Hilbert) — unblocks
   Amara correction #5 Option B; Aaron standing-approval
2. F# DSL for entry points + graph-query-language standards
   compliance (Cypher / GQL / Gremlin / SPARQL / Datalog)
3. LINQ-compatible entry points for C# consumers — pair with
   F# DSL; two frontends, one algebraic backend

6 of 8 Amara 17th-ferry corrections now shipped or confirmed:
Remaining: #6 ADR phrasing (already fine); #7 KSK naming
(BACKLOG #318 Max coord pending); #8 SOTA humility
(doc-phrasing discipline ongoing).

Build: 0 Warning / 0 Error.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(#333): 4 review-thread P1/P2s on robustZScore + coordinationRiskScoreRobust

Active PR-resolve-loop on #333.

1. Doc/impl contradiction on MAD=0 (thread 59VhYb, P1):
   RobustStats.robustZScore doc said "returns None when
   MAD(baseline)=0" but impl uses MadFloor and returns
   Some finite value. Rewrote doc to match impl:
   explicit "MadFloor substituted when MAD collapses to
   zero" — floor reflects "scale is below epsilon" not
   "undefined." Implementation is the contract.

2. Multi-enumeration of baseline seq (thread 59VhYq, P1):
   robustZScore previously passed `baseline` to both
   `median` + `mad` which each call `Seq.toArray`.
   Expensive AND inconsistent for lazy/non-repeatable
   sequences (different values between enumerations =
   undefined behavior). Fixed: `Seq.toArray` once at
   entry, pass the materialized array to both. O(n)
   instead of O(2n); stable across lazy sources.

3. Name attribution in Graph.fs doc comment (thread
   59VhY5, P1): "Amara 17th-ferry... Otto 18th
   graduation" → "external AI collaborator's 17th
   courier ferry... Eighteenth graduation under the
   Otto-105 cadence." Role-reference convention per
   AGENT-BEST-PRACTICES code/doc rule.

4. Array-vs-seq terminology (thread 59VhZG, P2):
   Graph.fs doc said callers "provide arrays" but the
   API is `double seq`. Rewrote: sequences + noted the
   materialize-once optimization in robustZScore so
   callers can pass any seq form without re-enumeration
   cost.

Thread 59VhX9 (P3-label-in-P2-section mismatch) — already
resolved on main via PR #341 which landed the signal-
processing row correctly labeled "P2 research-grade."
No fix needed on this branch.

Build: 0 Warning(s) / 0 Error(s). 53 RobustStats + Graph
tests pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…erry; candidate 5 of 5 closed

Bounded S-effort tick closing 8th-ferry candidate #5 via
PR #276 (5 rows added to TECH-RADAR: 4 Techniques
[semantic hashing / LSH / HNSW / PQ / quantum illumination]
+ 1 Tools/infra [Substrait]).

Quantum-illumination row preserves Amara's + AGENTS.md "do
not operationalize" discipline with explicit Hold-note for
long-range product claims per 2024 engineering review.

Key observations:

1. 8th-ferry queue: 1/5 closed (TECH-RADAR). Remaining: 3
   research docs + 1 future operational promotion; all
   within standing authority.
2. TECH-RADAR row-additions are lowest-cost highest-leverage
   "capture Amara's proposals" move; preserve provenance
   + future-discoverability; per-row research-effort
   deferred to warranted.
3. Quantum-illumination Assess-with-Hold-note is
   deterministic-reconciliation at TECH-RADAR layer — both
   directions preserved in same row so they can't drift.
4. Substrait Stronger-Assess flags P2 persistable-IR gap;
   strategic-scoping (Bonsai vs Substrait) without pre-
   committing.

Stacked on #275 (Otto-95 history).

…erry; candidate 5 of 5 closed

Bounded S-effort tick closing 8th-ferry candidate #5 via
PR #276 (5 rows added to TECH-RADAR: 4 Techniques
[semantic hashing / LSH / HNSW / PQ / quantum illumination]
+ 1 Tools/infra [Substrait]).

Quantum-illumination row preserves Amara's + AGENTS.md "do
not operationalize" discipline with explicit Hold-note for
long-range product claims per 2024 engineering review.

Key observations:

1. 8th-ferry queue: 1/5 closed (TECH-RADAR). Remaining: 3
   research docs + 1 future operational promotion; all
   within standing authority.
2. TECH-RADAR row-additions are lowest-cost highest-leverage
   "capture Amara's proposals" move; preserve provenance
   + future-discoverability; per-row research-effort
   deferred to warranted.
3. Quantum-illumination Assess-with-Hold-note is
   deterministic-reconciliation at TECH-RADAR layer — both
   directions preserved in same row so they can't drift.
4. Substrait Stronger-Assess flags P2 persistable-IR gap;
   strategic-scoping (Bonsai vs Substrait) without pre-
   committing.

Stacked on #275 (Otto-95 history).

…erry; candidate 5 of 5 closed

Bounded S-effort tick closing 8th-ferry candidate #5 via
PR #276 (5 rows added to TECH-RADAR: 4 Techniques
[semantic hashing / LSH / HNSW / PQ / quantum illumination]
+ 1 Tools/infra [Substrait]).

Quantum-illumination row preserves Amara's + AGENTS.md "do
not operationalize" discipline with explicit Hold-note for
long-range product claims per 2024 engineering review.

Key observations:

1. 8th-ferry queue: 1/5 closed (TECH-RADAR). Remaining: 3
   research docs + 1 future operational promotion; all
   within standing authority.
2. TECH-RADAR row-additions are lowest-cost highest-leverage
   "capture Amara's proposals" move; preserve provenance
   + future-discoverability; per-row research-effort
   deferred to warranted.
3. Quantum-illumination Assess-with-Hold-note is
   deterministic-reconciliation at TECH-RADAR layer — both
   directions preserved in same row so they can't drift.
4. Substrait Stronger-Assess flags P2 persistable-IR gap;
   strategic-scoping (Bonsai vs Substrait) without pre-
   committing.

Stacked on #275 (Otto-95 history).

…erry; candidate 5 of 5 closed

Bounded S-effort tick closing 8th-ferry candidate #5 via
PR #276 (5 rows added to TECH-RADAR: 4 Techniques
[semantic hashing / LSH / HNSW / PQ / quantum illumination]
+ 1 Tools/infra [Substrait]).

Quantum-illumination row preserves Amara's + AGENTS.md "do
not operationalize" discipline with explicit Hold-note for
long-range product claims per 2024 engineering review.

Key observations:

1. 8th-ferry queue: 1/5 closed (TECH-RADAR). Remaining: 3
   research docs + 1 future operational promotion; all
   within standing authority.
2. TECH-RADAR row-additions are lowest-cost highest-leverage
   "capture Amara's proposals" move; preserve provenance
   + future-discoverability; per-row research-effort
   deferred to warranted.
3. Quantum-illumination Assess-with-Hold-note is
   deterministic-reconciliation at TECH-RADAR layer — both
   directions preserved in same row so they can't drift.
4. Substrait Stronger-Assess flags P2 persistable-IR gap;
   strategic-scoping (Bonsai vs Substrait) without pre-
   committing.

Stacked on #275 (Otto-95 history).

…erry; candidate 5 of 5 closed

Bounded S-effort tick closing 8th-ferry candidate #5 via
PR #276 (5 rows added to TECH-RADAR: 4 Techniques
[semantic hashing / LSH / HNSW / PQ / quantum illumination]
+ 1 Tools/infra [Substrait]).

Quantum-illumination row preserves Amara's + AGENTS.md "do
not operationalize" discipline with explicit Hold-note for
long-range product claims per 2024 engineering review.

Key observations:

1. 8th-ferry queue: 1/5 closed (TECH-RADAR). Remaining: 3
   research docs + 1 future operational promotion; all
   within standing authority.
2. TECH-RADAR row-additions are lowest-cost highest-leverage
   "capture Amara's proposals" move; preserve provenance
   + future-discoverability; per-row research-effort
   deferred to warranted.
3. Quantum-illumination Assess-with-Hold-note is
   deterministic-reconciliation at TECH-RADAR layer — both
   directions preserved in same row so they can't drift.
4. Substrait Stronger-Assess flags P2 persistable-IR gap;
   strategic-scoping (Bonsai vs Substrait) without pre-
   committing.

Stacked on #275 (Otto-95 history).

…leration — 15th+16th graduation consolidated

Consolidates the DIRTY #329 cohesion primitives (Amara 17th-ferry
correction #3) with the new StakeCovariance module (Amara
correction #4).

Content from closed PR #329 (resurrect):
- Graph.internalDensity / exclusivity / conductance
- Wachs & Kertész 2019 cartel-detection cohesion/exclusivity
  replacing muddy 'subgraph entropy collapse'

NEW content (Amara correction #4):
- Zeta.Core.StakeCovariance module with:
  - windowedDeltaCovariance : int -> double[] -> double[] -> double option
    Pairwise cov over sliding window of stake-delta series
  - covarianceAcceleration : double option -> double option ->
    double option -> double option
    2nd-difference of three consecutive cov values
    (A(t) = C(t) - 2·C(t-1) + C(t-2))
  - aggregateAcceleration : Map<int * int, double> -> double option
    Mean pairwise acceleration over candidate group

Why a separate module: StakeCovariance operates on raw stake-
delta time series, not Graph edges. Composes WITH Graph via
downstream detector that combines graph signals + covariance
signals + sync signals into the full CoordinationRiskScore.

Addresses Amara's Part 2 correction #4 ambiguity: her Part 1
had 'C(t) = Cov({s_i(t)}, {s_j(t)})' which is undefined at a
single timepoint. This ship implements the windowed-delta +
2nd-difference formulation from her correction.

Tests (10 new, 44 total in GraphTests, all passing):
- internalDensity None on |S|<2
- internalDensity of K3 weight-10 ≈ 10
- exclusivity = 1 for isolated K3
- conductance < 0.1 for well-isolated subset
- windowedDeltaCovariance: None on too-small series
- windowedDeltaCovariance: high positive for synchronized motion
- windowedDeltaCovariance: negative for anti-correlated motion
- covarianceAcceleration = 2nd difference of cov series
- covarianceAcceleration None when any input missing
- aggregateAcceleration averages across pairs

4 of 8 Amara 17th-ferry corrections now shipped (#1 K₃=2 ✓,
conductance ✓, #4 windowed stake covariance acceleration ✓).
Remaining: #5 event→phase pipeline (future); #4 robust-z-score
variant of composite (future); #6 + #7 + #8 doc-phrasing /
BACKLOG.

Build: 0 Warning / 0 Error.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…erry; candidate 5 of 5 closed

Bounded S-effort tick closing 8th-ferry candidate #5 via
PR #276 (5 rows added to TECH-RADAR: 4 Techniques
[semantic hashing / LSH / HNSW / PQ / quantum illumination]
+ 1 Tools/infra [Substrait]).

Quantum-illumination row preserves Amara's + AGENTS.md "do
not operationalize" discipline with explicit Hold-note for
long-range product claims per 2024 engineering review.

Key observations:

1. 8th-ferry queue: 1/5 closed (TECH-RADAR). Remaining: 3
   research docs + 1 future operational promotion; all
   within standing authority.
2. TECH-RADAR row-additions are lowest-cost highest-leverage
   "capture Amara's proposals" move; preserve provenance
   + future-discoverability; per-row research-effort
   deferred to warranted.
3. Quantum-illumination Assess-with-Hold-note is
   deterministic-reconciliation at TECH-RADAR layer — both
   directions preserved in same row so they can't drift.
4. Substrait Stronger-Assess flags P2 persistable-IR gap;
   strategic-scoping (Bonsai vs Substrait) without pre-
   committing.

Stacked on #275 (Otto-95 history).

…erry; candidate 5 of 5 closed

Bounded S-effort tick closing 8th-ferry candidate #5 via
PR #276 (5 rows added to TECH-RADAR: 4 Techniques
[semantic hashing / LSH / HNSW / PQ / quantum illumination]
+ 1 Tools/infra [Substrait]).

Quantum-illumination row preserves Amara's + AGENTS.md "do
not operationalize" discipline with explicit Hold-note for
long-range product claims per 2024 engineering review.

Key observations:

1. 8th-ferry queue: 1/5 closed (TECH-RADAR). Remaining: 3
   research docs + 1 future operational promotion; all
   within standing authority.
2. TECH-RADAR row-additions are lowest-cost highest-leverage
   "capture Amara's proposals" move; preserve provenance
   + future-discoverability; per-row research-effort
   deferred to warranted.
3. Quantum-illumination Assess-with-Hold-note is
   deterministic-reconciliation at TECH-RADAR layer — both
   directions preserved in same row so they can't drift.
4. Substrait Stronger-Assess flags P2 persistable-IR gap;
   strategic-scoping (Bonsai vs Substrait) without pre-
   committing.

Stacked on #275 (Otto-95 history).

…~16 done)

Batched audit of the project-planning files. All classified
short-form since shape is factory-generic + content is
project-specific.

- GLOSSARY.md → both (coupled): format generic, Zeta-term
  entries specific
- ROUND-HISTORY.md → zeta-library-specific: Zeta's rounds
- BACKLOG.md → zeta-library-specific: ~6700 lines Zeta rows
- ROADMAP.md → zeta-library-specific: Zeta roadmap
- VISION.md → zeta-library-specific: Zeta vision, 11-pass
  editing history, Elisabeth dedication

Pattern after 15 audits (3 classes cleanly separated):
- 5 factory-generic (GOVERNANCE / AGENT-BEST-PRACTICES /
  ALIGNMENT / AUTONOMOUS-LOOP / FACTORY-HYGIENE)
- 6 both-coupled (CLAUDE / AGENTS / CONFLICT-RESOLUTION /
  WONT-DO / TECH-RADAR / GLOSSARY)
- 4 zeta-library-specific (ROUND-HISTORY / BACKLOG /
  ROADMAP / VISION)

15 of ~16 top-level files done. Remaining: directory-
level audits (.claude/skills/**, .claude/agents/**,
openspec/**, tools/**, .github/**).

Multi-repo split mechanical plan clearer:
- factory-generic → verbatim to Frontier (5 files)
- both-coupled → surgical edits per file, most to Frontier
  with Zeta content extracted (6 files)
- zeta-library-specific → stay in Zeta, Frontier gets
  empty templates (4 files)

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Sixth file audited. ALIGNMENT.md classified factory-
generic. Confirms the rule-substrate-instructional
hypothesis.

20 clauses (HC-1..HC-7, SD-1..SD-8, DIR-1..DIR-5) all
structurally instructional. Substance transfers to any
adopter; only project name + signatures + verbatim-quote
attributions are adopter-specific.

Refactor notes:
1. Substitute "Zeta" → <Project> in preamble + research-
   claim section + DIR-1 heading
2. Template-ify Signatures section (adopter fills in)
3. Keep Aaron verbatim quotes in Zeta repo's alignment
   contract as attribution anchors; Frontier template
   references "adopter's direct verbatim statements"
   as the pattern

Effort: S (simple project-name substitution + signatures
template-ify).

Six audits now complete. Pattern stable: instructional
→ factory-generic; state-logging / illustrative →
embedded Zeta-specifics.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…eneric)

Fifth file audited in gap #5. Confirms the rule-substrate-
instructional hypothesis.

29 BP-NN rules across 10 sections, all pure instructional:
skill-file hygiene / voice / state / security / knowledge
placement / testing / formal coverage / repo ontology /
operational standing / rule lifecycle / re-search-flag /
authoritative sources.

Zero rules embed Zeta-library-specific content. A handful
of rationales cite specific factory skills or ADRs
illustratively (BP-17 cites canonical-home-auditor SKILL;
BP-18 rationale mentions dotnet TreatWarningsAsErrors as
a gravity-comparison) — these are surgical generalisation
targets.

Effort: S (illustrative-reference generalisation only;
no rule substance changes).

Hypothesis confirmed: rule substrates with purely
instructional content are factory-generic by design.
Only rule substrates with state-logging content embed
project specifics (e.g. CONFLICT-RESOLUTION.md Active
Tensions).

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…eneric) (#184)

Fifth file audited in gap #5. Confirms the rule-substrate-
instructional hypothesis.

29 BP-NN rules across 10 sections, all pure instructional:
skill-file hygiene / voice / state / security / knowledge
placement / testing / formal coverage / repo ontology /
operational standing / rule lifecycle / re-search-flag /
authoritative sources.

Zero rules embed Zeta-library-specific content. A handful
of rationales cite specific factory skills or ADRs
illustratively (BP-17 cites canonical-home-auditor SKILL;
BP-18 rationale mentions dotnet TreatWarningsAsErrors as
a gravity-comparison) — these are surgical generalisation
targets.

Effort: S (illustrative-reference generalisation only;
no rule substance changes).

Hypothesis confirmed: rule substrates with purely
instructional content are factory-generic by design.
Only rule substrates with state-logging content embed
project specifics (e.g. CONFLICT-RESOLUTION.md Active
Tensions).

Attribution: Otto (loop-agent PM hat).

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Sixth file audited. ALIGNMENT.md classified factory-
generic. Confirms the rule-substrate-instructional
hypothesis.

20 clauses (HC-1..HC-7, SD-1..SD-8, DIR-1..DIR-5) all
structurally instructional. Substance transfers to any
adopter; only project name + signatures + verbatim-quote
attributions are adopter-specific.

Refactor notes:
1. Substitute "Zeta" → <Project> in preamble + research-
   claim section + DIR-1 heading
2. Template-ify Signatures section (adopter fills in)
3. Keep Aaron verbatim quotes in Zeta repo's alignment
   contract as attribution anchors; Frontier template
   references "adopter's direct verbatim statements"
   as the pattern

Effort: S (simple project-name substitution + signatures
template-ify).

Six audits now complete. Pattern stable: instructional
→ factory-generic; state-logging / illustrative →
embedded Zeta-specifics.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…~16 done)

Batched audit of the project-planning files. All classified
short-form since shape is factory-generic + content is
project-specific.

- GLOSSARY.md → both (coupled): format generic, Zeta-term
  entries specific
- ROUND-HISTORY.md → zeta-library-specific: Zeta's rounds
- BACKLOG.md → zeta-library-specific: ~6700 lines Zeta rows
- ROADMAP.md → zeta-library-specific: Zeta roadmap
- VISION.md → zeta-library-specific: Zeta vision, 11-pass
  editing history, Elisabeth dedication

Pattern after 15 audits (3 classes cleanly separated):
- 5 factory-generic (GOVERNANCE / AGENT-BEST-PRACTICES /
  ALIGNMENT / AUTONOMOUS-LOOP / FACTORY-HYGIENE)
- 6 both-coupled (CLAUDE / AGENTS / CONFLICT-RESOLUTION /
  WONT-DO / TECH-RADAR / GLOSSARY)
- 4 zeta-library-specific (ROUND-HISTORY / BACKLOG /
  ROADMAP / VISION)

15 of ~16 top-level files done. Remaining: directory-
level audits (.claude/skills/**, .claude/agents/**,
openspec/**, tools/**, .github/**).

Multi-repo split mechanical plan clearer:
- factory-generic → verbatim to Frontier (5 files)
- both-coupled → surgical edits per file, most to Frontier
  with Zeta content extracted (6 files)
- zeta-library-specific → stay in Zeta, Frontier gets
  empty templates (4 files)

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

… (batched)

Ninth + tenth audits in gap #5.

TECH-RADAR.md: both (coupled). ThoughtWorks-style radar
framework is factory-generic (Legend / Adopt-Trial-Assess-
Hold vocabulary / Usage). Entry rows heavily Zeta-library-
specific (DBSP / Z-sets / Bloom / FastCDC / etc.). Strategy:
Frontier inherits shape + empty Rings table stubs; Zeta
retains entry rows. Effort: S.

FACTORY-HYGIENE.md: factory-generic (self-classifying).
Every row already declares Scope (project/factory/both);
the file IS the factory's meta-hygiene substrate, by
construction. The split-execution plan reads directly off
the Scope column — no retrofit audit needed. Gold standard
for how rule substrates should be designed. Confirms gap

Progress: 10 of ~16 files audited (Otto-7/9/10/12/13/14/15/
16). Past the midpoint; ~6 files remaining. Projected
completion ~Otto-22.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…reclass + TECH-RADAR completeness

Drain all 6 review threads on gap #5 audit:

- Codex P1 (thread PRRT...9NJbm): reclassify FACTORY-HYGIENE
  from `factory-generic` + "Frontier as-is" to `both (coupled)`
  with asymmetric derivation (Frontier keeps canonical, Zeta
  derives project-scoped rows). Internal consistency with the
  Scope-column split manifest.
- Copilot P1 (thread ...LhE, outdated): Otto persona registry
  — out of scope for this PR; registration is backlog-level
  work tracked separately. Acknowledging for audit-trail only.
- Copilot P1 (thread ...LhG): TECH-RADAR length corrected
  (122 -> 128 lines) and "Legend + Rings ... + Usage" summary
  expanded to include Upstreams / Hardware intrinsics.
- Copilot P1 (thread ...LhS): TECH-RADAR section-by-section
  table expanded with two missing section rows (Upstreams /
  prior art; Hardware intrinsics / platform).
- Copilot P2 (thread ...LiC): FACTORY-HYGIENE length corrected
  (203 -> 206 lines; file grew on main between audit and now).
- Copilot P1 (thread ...LiT): FACTORY-HYGIENE post-split plan
  rewritten for internal consistency — Frontier keeps canonical,
  Zeta derives; "Ships to project-under-construction" is a
  Frontier-only projection over the canonical table.

Rebased onto origin/main; resolved merge-list conflict in
"Files audited" section preserving both sets of additions.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…generic)

Third file audited in gap #5. Breaks the both-coupled
pattern from CLAUDE.md + AGENTS.md.

GOVERNANCE.md classified factory-generic overall:
- 28 of 32 rules: purely factory-generic
- 4 rules: "both" with surgical notes (§19 public API /
  §24 dev setup / §28 OpenSpec / §29 backlog files) —
  pattern generic, illustrative examples Zeta-specific

Post-split location: Frontier as-is. 4 small inline
placeholder edits, estimated refactor effort S.

The factory's rule substrate is abstract by design; rules
shape behaviour without enforcing project-specifics.
Adopters substitute their own libraries / install steps /
specs while inheriting the rule shape.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…generic) (#181)

Third file audited in gap #5. Breaks the both-coupled
pattern from CLAUDE.md + AGENTS.md.

GOVERNANCE.md classified factory-generic overall:
- 28 of 32 rules: purely factory-generic
- 4 rules: "both" with surgical notes (§19 public API /
  §24 dev setup / §28 OpenSpec / §29 backlog files) —
  pattern generic, illustrative examples Zeta-specific

Post-split location: Frontier as-is. 4 small inline
placeholder edits, estimated refactor effort S.

The factory's rule substrate is abstract by design; rules
shape behaviour without enforcing project-specifics.
Adopters substitute their own libraries / install steps /
specs while inheriting the rule shape.

Attribution: Otto (loop-agent PM hat).

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…~16 done)

Batched audit of the project-planning files. All classified
short-form since shape is factory-generic + content is
project-specific.

- GLOSSARY.md → both (coupled): format generic, Zeta-term
  entries specific
- ROUND-HISTORY.md → zeta-library-specific: Zeta's rounds
- BACKLOG.md → zeta-library-specific: ~6700 lines Zeta rows
- ROADMAP.md → zeta-library-specific: Zeta roadmap
- VISION.md → zeta-library-specific: Zeta vision, 11-pass
  editing history, Elisabeth dedication

Pattern after 15 audits (3 classes cleanly separated):
- 5 factory-generic (GOVERNANCE / AGENT-BEST-PRACTICES /
  ALIGNMENT / AUTONOMOUS-LOOP / FACTORY-HYGIENE)
- 6 both-coupled (CLAUDE / AGENTS / CONFLICT-RESOLUTION /
  WONT-DO / TECH-RADAR / GLOSSARY)
- 4 zeta-library-specific (ROUND-HISTORY / BACKLOG /
  ROADMAP / VISION)

15 of ~16 top-level files done. Remaining: directory-
level audits (.claude/skills/**, .claude/agents/**,
openspec/**, tools/**, .github/**).

Multi-repo split mechanical plan clearer:
- factory-generic → verbatim to Frontier (5 files)
- both-coupled → surgical edits per file, most to Frontier
  with Zeta content extracted (6 files)
- zeta-library-specific → stay in Zeta, Frontier gets
  empty templates (4 files)

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

… (batched)

Ninth + tenth audits in gap #5.

TECH-RADAR.md: both (coupled). ThoughtWorks-style radar
framework is factory-generic (Legend / Adopt-Trial-Assess-
Hold vocabulary / Usage). Entry rows heavily Zeta-library-
specific (DBSP / Z-sets / Bloom / FastCDC / etc.). Strategy:
Frontier inherits shape + empty Rings table stubs; Zeta
retains entry rows. Effort: S.

FACTORY-HYGIENE.md: factory-generic (self-classifying).
Every row already declares Scope (project/factory/both);
the file IS the factory's meta-hygiene substrate, by
construction. The split-execution plan reads directly off
the Scope column — no retrofit audit needed. Gold standard
for how rule substrates should be designed. Confirms gap

Progress: 10 of ~16 files audited (Otto-7/9/10/12/13/14/15/
16). Past the midpoint; ~6 files remaining. Projected
completion ~Otto-22.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…reclass + TECH-RADAR completeness

Drain all 6 review threads on gap #5 audit:

- Codex P1 (thread PRRT...9NJbm): reclassify FACTORY-HYGIENE
  from `factory-generic` + "Frontier as-is" to `both (coupled)`
  with asymmetric derivation (Frontier keeps canonical, Zeta
  derives project-scoped rows). Internal consistency with the
  Scope-column split manifest.
- Copilot P1 (thread ...LhE, outdated): Otto persona registry
  — out of scope for this PR; registration is backlog-level
  work tracked separately. Acknowledging for audit-trail only.
- Copilot P1 (thread ...LhG): TECH-RADAR length corrected
  (122 -> 128 lines) and "Legend + Rings ... + Usage" summary
  expanded to include Upstreams / Hardware intrinsics.
- Copilot P1 (thread ...LhS): TECH-RADAR section-by-section
  table expanded with two missing section rows (Upstreams /
  prior art; Hardware intrinsics / platform).
- Copilot P2 (thread ...LiC): FACTORY-HYGIENE length corrected
  (203 -> 206 lines; file grew on main between audit and now).
- Copilot P1 (thread ...LiT): FACTORY-HYGIENE post-split plan
  rewritten for internal consistency — Frontier keeps canonical,
  Zeta derives; "Ships to project-under-construction" is a
  Frontier-only projection over the canonical table.

Rebased onto origin/main; resolved merge-list conflict in
"Files audited" section preserving both sets of additions.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Sixth file audited. ALIGNMENT.md classified factory-
generic. Confirms the rule-substrate-instructional
hypothesis.

20 clauses (HC-1..HC-7, SD-1..SD-8, DIR-1..DIR-5) all
structurally instructional. Substance transfers to any
adopter; only project name + signatures + verbatim-quote
attributions are adopter-specific.

Refactor notes:
1. Substitute "Zeta" → <Project> in preamble + research-
   claim section + DIR-1 heading
2. Template-ify Signatures section (adopter fills in)
3. Keep Aaron verbatim quotes in Zeta repo's alignment
   contract as attribution anchors; Frontier template
   references "adopter's direct verbatim statements"
   as the pattern

Effort: S (simple project-name substitution + signatures
template-ify).

Six audits now complete. Pattern stable: instructional
→ factory-generic; state-logging / illustrative →
embedded Zeta-specifics.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Aaron 2026-04-23 directive (two parts):

> we should do a review of our database and come up with backlog items
> where we are lacking it's not cutting edge, we need more research etc

> on some cadence look at the last few things that went into master
> and make sure its not overwhelemginly speculative. thats a smell
> that our software factor is live locked.

## Live-lock audit tool (internal priority)

`tools/audit/live-lock-audit.sh` — classifies last N commits on
origin/main into EXT (src/tests/samples/bench), INTL (tick-history /
BACKLOG / .claude / round-history), SPEC (research / memory / DECISIONS),
OTHR. Flags smell when EXT < 20%. Tunable via LIVELOCK_MIN_EXT_PCT.

**Inaugural run (landed in `docs/hygiene-history/live-lock-audit-
history.md`):** EXT 0%, INTL 72%, SPEC 16%, OTHR 12% on last 25 main
commits. **Smell fires.** Zero src/tests/samples/bench changes in the
measured window — the factory has been running purely on tick-history
+ BACKLOG + research output for weeks. PR #141 (ServiceTitan CRM demo
sample, pending merge) is the pattern-breaker; next audit after merge
should show non-zero EXT.

## Cutting-edge DB gap review (Aaron-directed)

`docs/research/cutting-edge-database-gap-review-2026-04-23.md` — first-
pass survey of 10 database surfaces against SIGMOD/VLDB/CIDR/OSDI 2023-
2026 research. Key gaps named (each with paper anchor):

  1. Object-store-backed Spine (Delta Lake / Iceberg / Hudi frontier)
  2. Compiled / JIT execution (Umbra Flying Start, Photon)
  3. io_uring native async disk (Linux frontier)
  4. CXL memory tiering (Pond, ASPLOS 2023)
  5. Learned cost-model framework (Bao, LOGER)
  6. Deterministic-execution mode (Calvin, Polyjuice, TigerBeetle)
  7. Retraction-weight compression (ALP, SIGMOD 2023)
  8. Xor / Binary Fuse filters, DDSketch
  9. RDMA-native operator transport (FaRMv2, SSD-RDMA)
 10. Power-loss-tested durability (TigerBeetle gold standard)

Top 3 filed as concrete BACKLOG P2 rows with research anchors:

- **#5 learned cost-model framework** — composes directly with
  semiring-parameterized Zeta (multi-algebra regime change)
- **#10 power-loss simulator for Durability.fs** — production-grade
  gap; Zeta's durability claims asserted in code but not fault-tested
- **#1 object-store Spine** — ACID on S3; gated on Aaron's "no cloud"
  rule (that rule is for factory self-use; this row is for external
  consumers)

Live-lock-smell row also filed as P1 Factory/tooling.

## What this does NOT do

- Not a commitment to land any DB gap this round. Aaron gates.
- Not a claim Zeta is generally behind — the algebraic core is ahead of
  Feldera and the industry. Gaps are on the engineering substrate.
- Not exhaustive — 10 surfaces reviewed; more exist. Cadence suggests
  every 3-5 rounds.

## Meta note

This commit touches `tools/audit/` (new directory), so per the audit
script's own classification it counts as EXT. The next audit run after
this lands should show EXT > 0%.

Composes with:
- memory/project_aaron_external_priority_stack_and_live_lock_smell_2026_04_23.md
- memory/project_semiring_parameterized_zeta_regime_change_one_algebra_to_map_others_2026_04_22.md
- memory/feedback_samples_readability_real_code_zero_alloc_2026_04_22.md

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Aaron 2026-04-23 directive (two parts):

> we should do a review of our database and come up with backlog items
> where we are lacking it's not cutting edge, we need more research etc

> on some cadence look at the last few things that went into master
> and make sure its not overwhelemginly speculative. thats a smell
> that our software factor is live locked.

## Live-lock audit tool (internal priority)

`tools/audit/live-lock-audit.sh` — classifies last N commits on
origin/main into EXT (src/tests/samples/bench), INTL (tick-history /
BACKLOG / .claude / round-history), SPEC (research / memory / DECISIONS),
OTHR. Flags smell when EXT < 20%. Tunable via LIVELOCK_MIN_EXT_PCT.

**Inaugural run (landed in `docs/hygiene-history/live-lock-audit-
history.md`):** EXT 0%, INTL 72%, SPEC 16%, OTHR 12% on last 25 main
commits. **Smell fires.** Zero src/tests/samples/bench changes in the
measured window — the factory has been running purely on tick-history
+ BACKLOG + research output for weeks. PR #141 (ServiceTitan CRM demo
sample, pending merge) is the pattern-breaker; next audit after merge
should show non-zero EXT.

## Cutting-edge DB gap review (Aaron-directed)

`docs/research/cutting-edge-database-gap-review-2026-04-23.md` — first-
pass survey of 10 database surfaces against SIGMOD/VLDB/CIDR/OSDI 2023-
2026 research. Key gaps named (each with paper anchor):

  1. Object-store-backed Spine (Delta Lake / Iceberg / Hudi frontier)
  2. Compiled / JIT execution (Umbra Flying Start, Photon)
  3. io_uring native async disk (Linux frontier)
  4. CXL memory tiering (Pond, ASPLOS 2023)
  5. Learned cost-model framework (Bao, LOGER)
  6. Deterministic-execution mode (Calvin, Polyjuice, TigerBeetle)
  7. Retraction-weight compression (ALP, SIGMOD 2023)
  8. Xor / Binary Fuse filters, DDSketch
  9. RDMA-native operator transport (FaRMv2, SSD-RDMA)
 10. Power-loss-tested durability (TigerBeetle gold standard)

Top 3 filed as concrete BACKLOG P2 rows with research anchors:

- **#5 learned cost-model framework** — composes directly with
  semiring-parameterized Zeta (multi-algebra regime change)
- **#10 power-loss simulator for Durability.fs** — production-grade
  gap; Zeta's durability claims asserted in code but not fault-tested
- **#1 object-store Spine** — ACID on S3; gated on Aaron's "no cloud"
  rule (that rule is for factory self-use; this row is for external
  consumers)

Live-lock-smell row also filed as P1 Factory/tooling.

## What this does NOT do

- Not a commitment to land any DB gap this round. Aaron gates.
- Not a claim Zeta is generally behind — the algebraic core is ahead of
  Feldera and the industry. Gaps are on the engineering substrate.
- Not exhaustive — 10 surfaces reviewed; more exist. Cadence suggests
  every 3-5 rounds.

## Meta note

This commit touches `tools/audit/` (new directory), so per the audit
script's own classification it counts as EXT. The next audit run after
this lands should show EXT > 0%.

Composes with:
- memory/project_aaron_external_priority_stack_and_live_lock_smell_2026_04_23.md
- memory/project_semiring_parameterized_zeta_regime_change_one_algebra_to_map_others_2026_04_22.md
- memory/feedback_samples_readability_real_code_zero_alloc_2026_04_22.md

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Aaron 2026-04-23 directive (two parts):

> we should do a review of our database and come up with backlog items
> where we are lacking it's not cutting edge, we need more research etc

> on some cadence look at the last few things that went into master
> and make sure its not overwhelemginly speculative. thats a smell
> that our software factor is live locked.

## Live-lock audit tool (internal priority)

`tools/audit/live-lock-audit.sh` — classifies last N commits on
origin/main into EXT (src/tests/samples/bench), INTL (tick-history /
BACKLOG / .claude / round-history), SPEC (research / memory / DECISIONS),
OTHR. Flags smell when EXT < 20%. Tunable via LIVELOCK_MIN_EXT_PCT.

**Inaugural run (landed in `docs/hygiene-history/live-lock-audit-
history.md`):** EXT 0%, INTL 72%, SPEC 16%, OTHR 12% on last 25 main
commits. **Smell fires.** Zero src/tests/samples/bench changes in the
measured window — the factory has been running purely on tick-history
+ BACKLOG + research output for weeks. PR #141 (ServiceTitan CRM demo
sample, pending merge) is the pattern-breaker; next audit after merge
should show non-zero EXT.

## Cutting-edge DB gap review (Aaron-directed)

`docs/research/cutting-edge-database-gap-review-2026-04-23.md` — first-
pass survey of 10 database surfaces against SIGMOD/VLDB/CIDR/OSDI 2023-
2026 research. Key gaps named (each with paper anchor):

  1. Object-store-backed Spine (Delta Lake / Iceberg / Hudi frontier)
  2. Compiled / JIT execution (Umbra Flying Start, Photon)
  3. io_uring native async disk (Linux frontier)
  4. CXL memory tiering (Pond, ASPLOS 2023)
  5. Learned cost-model framework (Bao, LOGER)
  6. Deterministic-execution mode (Calvin, Polyjuice, TigerBeetle)
  7. Retraction-weight compression (ALP, SIGMOD 2023)
  8. Xor / Binary Fuse filters, DDSketch
  9. RDMA-native operator transport (FaRMv2, SSD-RDMA)
 10. Power-loss-tested durability (TigerBeetle gold standard)

Top 3 filed as concrete BACKLOG P2 rows with research anchors:

- **#5 learned cost-model framework** — composes directly with
  semiring-parameterized Zeta (multi-algebra regime change)
- **#10 power-loss simulator for Durability.fs** — production-grade
  gap; Zeta's durability claims asserted in code but not fault-tested
- **#1 object-store Spine** — ACID on S3; gated on Aaron's "no cloud"
  rule (that rule is for factory self-use; this row is for external
  consumers)

Live-lock-smell row also filed as P1 Factory/tooling.

## What this does NOT do

- Not a commitment to land any DB gap this round. Aaron gates.
- Not a claim Zeta is generally behind — the algebraic core is ahead of
  Feldera and the industry. Gaps are on the engineering substrate.
- Not exhaustive — 10 surfaces reviewed; more exist. Cadence suggests
  every 3-5 rounds.

## Meta note

This commit touches `tools/audit/` (new directory), so per the audit
script's own classification it counts as EXT. The next audit run after
this lands should show EXT > 0%.

Composes with:
- memory/project_aaron_external_priority_stack_and_live_lock_smell_2026_04_23.md
- memory/project_semiring_parameterized_zeta_regime_change_one_algebra_to_map_others_2026_04_22.md
- memory/feedback_samples_readability_real_code_zero_alloc_2026_04_22.md

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>